Skip to content

chore: merge release into master #4281

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jan 11, 2019

Conversation

DimitarTachev
Copy link
Contributor

No description provided.

DimitarTachev and others added 6 commits January 10, 2019 11:36
We don't need the AttachAvailability response as now we don't need different actions based on the response. We just need to get the debug port which is printed by the AttachRequest and the Runtime is now accepting connections regardless of its state. This also allows us to remove the availability calls from the runtime.
…ssues with multiple device socket connections and attach requests, remove all locks on process exit
@DimitarTachev DimitarTachev merged commit f4768e0 into master Jan 11, 2019
@DimitarTachev DimitarTachev deleted the tachev/merge-release-into-master branch January 11, 2019 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants